Systems and methods for generating and presenting graphical user interfaces

ABSTRACT

Systems and methods for presenting graphical user interfaces corresponding to users and including portions of one or more chat sessions the users are participants in, the chat sessions facilitating synchronous textual communication between the users that takes place through a chat system are disclosed. Some implementations may: obtain chat information characterizing participants in the chat sessions; and effectuate presentation, responsive to receiving user input indicating a selection of the first user by the second user, of a first graphical user interface corresponding to the first user via a client computing platform associated with the second user.

FIELD OF THE DISCLOSURE

The present disclosure relates to systems and methods for generating and presenting graphical user interfaces corresponding to users and including portions of one or more chat sessions the users are participants in.

BACKGROUND

Chat applications and/or systems may facilitate synchronous textual communications between two or more users. Graphical user interfaces presenting chat sessions may present the textual communications sent by each user in real-time and/or near real-time. Typical graphical user interfaces present chat sessions having one or more different participants as separate windows and/or graphical user interfaces.

Group chat sessions may facilitate synchronous textual communications between a group of users. New groups with one or more different users may be created such that users often participate in multiple chat sessions with different individual other users and/or groups of users.

SUMMARY

One aspect of the present disclosure relates to a system configured for presenting graphical user interfaces corresponding to users. The graphical user interfaces may include portions of one or more chat sessions the users are participants in. The chat sessions may facilitate synchronous textual communication between the users that takes place through a chat system. The chat system may be part of the system and/or external to the claimed system. The system may include one or more hardware processors configured by machine-readable instructions. The processor(s) may be configured to obtain chat information characterizing participants in the chat sessions. The chat sessions may include a first chat session, a second chat session, and/or other chat sessions. The first chat session may facilitate synchronous textual communication between a first user, a second user, and a third user, such that first chat information characterizing the first user, the second user, and the third user as participants in the first chat session is obtained. The second chat session may facilitate synchronous textual communication between the first user and the second user such that second chat information characterizing the first user and the second user as participants in the second chat session is obtained.

Responsive to receiving user input indicating a section of the first user by the second user, the processor(s) may be configured to effectuate presentation of a first graphical user interface corresponding to the first user via a client computing platform associated with the second user. The first graphical user interface may include first stated information provided by the first user and portions of one or more chat sessions the first user is a participant in with the second user, such that the first graphical user interface displays the first stated information characterizing the first user, at least a portion of the first chat session, and at least a portion of the second chat session.

Another aspect of the present disclosure relates to a method for presenting graphical user interfaces corresponding to users and including portions of one or more chat sessions the users are participants in, the chat sessions facilitating synchronous textual communication between the users that takes place through a chat system. The method may include obtaining chat information characterizing participants in the chat sessions. The chat sessions may include a first chat session, a second chat session, a third chat session, and/or other chat sessions. The first chat session may facilitate synchronous textual communication between a first user, a second user, and a third user, such that first chat information characterizing the first user, the second user, and the third user as participants in the first chat session is obtained. The second chat session may facilitate synchronous textual communication between the first user and the second user such that second chat information characterizing the first user and the second user as participants in the second chat session may be obtained.

The method may include effectuating presentation of a first graphical user interface corresponding to the first user via a client computing platform associated with the second user. The graphical user interfaces may correspond to individual ones of the selected users and individual ones of the selecting users. For example, the first graphical user interface corresponding to the first user may be presented via the client computing platform associated with the second user responsive to receiving user input indicating a selection of the first user by the second user. The first graphical user interface may include first stated information provided by the first user, portions of one or more chat sessions the first user is a participant in with the second user, and/or other information. As such, the first graphical user interface may display the first stated information characterizing the first user, at least a portion of the first chat session, at least a portion of the second chat session, and/or other information.

In some implementations, a system configured to present graphical user interfaces corresponding to users that including portions of one or more chat sessions the users are participants in, may include one or more of: one or more servers, one or more client computing platforms, and/or other components. The one or more servers may be configured to communicate with one or more client computing platforms according to a client/server architecture and/or other architecture. The one or more servers and/or client computing platforms may include one or more physical processors configured to execute one or more computer program components. The computer program components may include one or more of an environment state component, a chat component, a user selection component, a unit of work component, a graphical user interface component, and/or other components.

The environment state component may be configured to manage environment state information for maintaining a collaboration environment. The environment state information may include user records, work unit records, and/or other records. The environment state information may define a state of the collaboration environment including user states, work unit states, and/or other states. The user states may be defined by the user records. The user records may define values of user parameters associated with users interacting with and/or viewing the collaboration environment. The work unit states may be defined by the work unit records that define values of work unit parameters for units of work managed, created, and/or assigned within the collaboration environment.

In some implementations, the user records may include stated information characterizing the users that is provided by the users. First stated information may include information selected by the first user that characterizes the first user. By way of example, the first stated information may include username information, title information, department information, status information, work information, and/or other information.

The chat component may be configured to obtain chat information characterizing participants in one or more chat sessions. The chat sessions may include a first chat session, a second chat session, and/or other chat sessions. The chat sessions may facilitate synchronous textual communication between two or more users. By way of example, a first chat session may facilitate synchronous textual communication between the first user, a second user, and/or a third user. Chat information characterizing the first user, the second user, and/or the third user as participants in the first chat session may be obtained. By way of another example, a second chat session may facilitate textual communication between the first user and the second user. As such, second chat information characterizing the first user and the second user as participants in the second chat session may be obtained.

The user selection component may be configured to receive user input indicating selection of one or more users by one or more other users. A given user may select another user to view a graphical user interface corresponding to the other user. The graphical user interface corresponding to the other user may include information associated with one or both of the given user and the other user. For example, information associated with both the given user and the other user may include portions of one or more chat sessions the given user is a participant in with the other user, one or more units of work both the given user and the other user are associated with, and/or other information. The user selection component may be configured to receive user input indicating a selection of the first user by the second user. User input indicating selection of the first user by the second user may be received from a client computing platform associated with the second user. In some implementations, the user selection component may be configured to receive and/or execute search queries for one or more users.

The unit of work component may be configured to identify one or more units of work associated with the first user based on the work unit records and/or the user records.

The graphical user interface component may be configured to effectuate presentation of a first graphical user interface corresponding to the first user. Presentation of the first graphical user interface may be effectuated responsive to the user selection component receiving selection of the first user by the second user. The first graphical user interface may be presented via a client computing platform associated with the second user. The graphical user interface may include first stated information provided by the first user, portions of one or more chat sessions the first user is a participant in with the second user, and/or other information. As such, for example, the first graphical user interface may display the first data information characterizing the first user, at least a portion of the first chat session, at least a portion of the second chat session, and/or other information.

These and other features, and characteristics of the present technology, as well as the methods of operation and functions of the related elements of structure and the combination of parts and economies of manufacture, will become more apparent upon consideration of the following description and the appended claims with reference to the accompanying drawings, all of which form a part of this specification, wherein like reference numerals designate corresponding parts in the various figures. It is to be expressly understood, however, that the drawings are for the purpose of illustration and description only and are not intended as a definition of the limits of the invention. As used in the specification and in the claims, the singular form of “a”, “an”, and “the” include plural referents unless the context clearly dictates otherwise.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 shows a system configured for generating and presenting graphical user interfaces corresponding to users and including portions of one or more chat sessions the users are participants in, the chat sessions facilitating synchronous textual communication between the users that takes place through a chat system, in accordance with one or more implementations.

FIG. 2 illustrates a graphical user interface corresponding to user 1 and including portions of one or more chat sessions user 1 and user 2 are participants in, in accordance with one or more implementations.

FIG. 3 illustrates a graphical user interface corresponding to user 1 and including portions of one or more chat sessions user 1 and user 2 are participants in, in accordance with one or more implementations.

FIG. 4 includes a flow chart of a method for generating and presenting graphical user interfaces corresponding to users and including portions of one or more chat sessions the users are participants in, the chat sessions facilitating synchronous textual communication between the users that takes place through a chat system, in accordance with one or more implementations.

FIG. 5 includes a flow chart of a method for generating and presenting graphical user interfaces corresponding to users and including portions of one or more chat sessions the users are participants in, the chat sessions facilitating synchronous textual communication between the users that takes place through a chat system, in accordance with one or more implementations.

DETAILED DESCRIPTION

FIG. 1 illustrates a system 100 configured for presenting graphical user interfaces corresponding to users and including portions of one or more chat sessions the users are participants in, the chat sessions facilitating synchronous textual communication between the users that takes place through a chat system, in accordance with one or more implementations. In some implementations, system 100 may include one or more servers 102. Server(s) 102 may be configured to communicate with one or more client computing platforms 104 according to a client/server architecture and/or other architectures. Client computing platform(s) 104 may be configured to communicate with other client computing platforms via server(s) 102 and/or according to a peer-to-peer architecture and/or other architectures. Users may access system 100 via client computing platform(s) 104.

Server(s) 102 may be configured by machine-readable instructions 106. Machine-readable instructions 106 may include one or more instruction components. The instruction components may include computer program components. The instruction components may include one or more of an environment state component 108, chat component 110, user selection component 112, unit of work component 114, graphical user interface component 116, and/or other instruction components.

Environment state component 108 may be configured to manage environment state information to maintain a collaboration environment. The environment state information may include user records and work unit records. The environment state information may define a state of the collaboration environment including user states, work unit states, and/or other states. The user states may be defined by the user records that define values of user parameters associated with users interacting with and/or viewing the collaboration environment. Individual ones of the user records may correspond to individual ones of the users. The work unit states may be defined by the work unit records that define values of work unit parameters for units of work managed, created, and/or assigned within the collaboration environment. Individual ones of the work unit records may correspond to individual ones of the units of work and/or be associated with one or more users and/or other units of work.

The environment state information may include user records, work unit records, and/or other records. The environment state information may be continuously generated and/or updated based on the state of the collaboration environment representing the users' interactions with the collaboration environment. The state of the collaboration environment may include a user state, a work unit state, and/or other states. The user state may be defined by the user records. The user records may define values of user parameters associated with users interacting with and/or viewing the collaboration environment. The work unit state may be defined by the work unit records. The work unit records may define values of work unit parameters for units of work managed, created, and/or assigned within the collaboration environment. In some implementations, the work unit state may include a project state, a task state, a sub-task state, and/or other states. The work unit records may include project records, task records, sub-task records, and/or other records.

The work unit parameters for work units managed, created, and/or assigned within the collaboration environment may include parameters describing one or more work units managed, created, and/or assigned within the collaboration environment and/or via the collaboration work management platform, and/or the metadata associated with the one or more work units. Individual ones of the work units may be associated with individual ones of the work unit records. A work unit record may define values of the work unit parameters associated with a given work unit managed, created, and/or assigned within the collaboration environment and/or via the collaboration work management platform. A given work unit may have one or more owners and/or one or more team members working on the given work unit. Work units may include one or more to-do items, action items, objectives, and/or other units of work one or more users should accomplish and/or plan on accomplishing. Units of work may be created by a given user for the given user and/or created by the given user and assigned to one or more other users. A given work unit may include one or more projects, tasks, sub-tasks, and/or other units of work possibly assigned to and/or associated with one or more users.

The work unit parameters may, by way of non-limiting example, include one or more of: one or more units of work, one or more user comment parameters (e.g., a creator, a recipient, one or more followers, one or more other interested parties, content, one or more times, up-votes, other hard-coded responses, etc.), a work unit name, a work unit description, one or more work unit dates (e.g., a start date, a due date, a completion date, and/or other work unit dates), one or more members associated with a unit of work (e.g., an owner, one or more other project/task members, member access information, and/or other work unit members and/or member information), a status and/or progress (e.g., an update, a hardcoded status update, a measured status, quantity of work units remaining in a given project, completed work units in a given project, and/or other status parameter), one or more attachments, notification settings, privacy, an associated URL, one or more interaction parameters (e.g., sources of the interactions, context of the interactions, content of the interactions, time for the interactions, and/or other interaction parameters), updates, ordering of units of work within a given unit of work (e.g., tasks within a project, sub-tasks within a task, etc.), state of a workspace for a given unit of work (e.g., application state parameters, application status, application interactions, user information, and/or other parameters related to the state of the workspace for a unit of work), dependencies between one or more work units, one or more custom fields (e.g., priority, cost, stage, and/or other custom fields), other work unit parameters for the given work units, and/or other work unit parameters, and/or user parameters for one or more users and/or work units the given project is associated with.

The user parameters associated with the users interacting with and/or viewing the collaboration environment may include parameters describing the users, their actions within the collaboration environment, their settings, and/or other user information; and/or metadata associated with the users, their actions within the environment, their settings, and/or other user information. Individual ones of the users may be associated with individual ones of the user records. A user record may define values of the user parameters associated with a given user interacting with and/or viewing the collaboration environment.

The user parameters may, by way of non-limiting example, include one or more of: a user name, a group parameter, a subset parameter, a user account, a user role, a user department, descriptive user content, a to-email, a from-email, a photo, an organization, a workspace, one or more projects (which may include project parameters defined by one or more work unit records), one or more items of work (which may include one or more unit of work parameters defined by one or more unit of work records), one or more user comments, one or more teams the user belongs to, one or more of the user display settings (e.g., colors, size, project order, task order, other work unit order, etc.), one or more authorized applications, one or more presence/interaction parameters (e.g., indicating presence and/or interaction level at an environment level, work unit level, project level, task level, application level, etc.), one or more notification settings, one or more progress parameters, status information for one or more work units the user is associated with, one or more statistics related to a given user (e.g., how many units of work the user has completed, how quickly the user completed the units of work, how quickly the user completes certain types of work units, the efficiency of the user, bandwidth of the user, activity level of the user, etc.), application access information (e.g., username/password for one or more third-party applications), one or more favorites and/or priorities, other user parameters for the given user, and/or other user parameters and/or work unit parameters, for one or more work units the given user is associated with.

Chat component 110 may be configured to obtain chat information characterizing participants in the chat sessions. Chat sessions may include synchronous and/or semi-synchronous textual conversations between two or more users via a chat system and/or a chat interface. In some implementations, the chat sessions may facilitate textual communication and/or non-textual communication between two or more users. For example, audio communication, video communication and/or other types of communication may be facilitated by the chat sessions. The chat information may include user information characterizing the participants in the chat sessions, text information representing the textual communications exchanged during the chat sessions, time information indicating a date and/or time the textual communications were exchanged, natural language processing information characterizing the audio and/or video communications that occurred during the chat sessions, and/or other information. Chat component 110 may be configured to perform natural language processing of any audio and/or video communications that occur during the chat sessions to generate natural language processing information.

The chat sessions may include a first chat session, a second chat session, a third chat session, a fourth session, a fifth chat session, and/or any other chat session. By way of non-limiting example, the first chat session may facilitate synchronous textual communication between a first user, a second user, and a third user. As such, the first chat information may characterize the first user, the second user, and the third user as participants in the first chat session is. The first chat information may be obtained by chat component 110. The first chat information may be obtained by chat component 110 so it may be included in graphical user interfaces corresponding to the first user, the second user, and/or the third user, responsive to the first user, the second user, and/or the third user selecting one of the first user, the second user, and/or the third user. The second chat session may facilitate synchronous textual communication between the first user and the second user such that second chat information characterizing the first user and the second user as participants in the second chat session is obtained.

In some implementations, chat component 110 may be configured to implement an instance of a chat session to facilitate the synchronous communication between the users within the collaboration environment. Implementing instances of the chat sessions may include transmitting the textual communications that make up the chat sessions to the client computing platforms for presentation through graphical chat interfaces. In some implementations, chat component 110 may be configured to receive and/or obtain chat information from a chat system external to the collaboration environment. By way of non-limiting example, a chat system external to the collaboration environment may integrate with and/or communicate with the collaboration environment via an Application Program Interface (API).

User selection component 112 may be configured to receive user input indicating selection of one or more users. The one or more users may be selected by one or more other users. A given user may select another user to view a graphical user interface corresponding to the other user and the given user. The graphical user interface corresponding to the other user may include information associated with both the given user and the other user. The information associated with both the given user and the other user may include portions of one or more chat sessions the given user is a participant in with the other user, one or more units of work both the given user and the other user are associated with, and/or other information. User selection component 112 may be configured to receive user input indicating a selection of the first user by the second user. User input indicating selection of the first user by the second user may be received from a client computing platform associated with the second user.

In some implementations, user selection component 112 may be configured to receive and/or execute search queries for one or more users. Responsive to receiving a search query, user selection component 112 may identify one or more users corresponding to the search query and initiate presentation of results for the search query. The results for the search query may include one or more users matching the search query. User selection component 112 may be configured to receive user input indicating selection of a user from the results for the search query.

In some implementations, unit of work component 114 may be configured to identify one or more of the units of work associated with the selected users and/or the selecting users. Units of work associated with one or more users may include units of work one or more users assigned to another user, are working on, assigned to, responsible for, overseeing, managing, and/or otherwise associated with. For example, units of work associated with both the selected user and the selecting user unit of work component 114 may be configured to identify one or more units of work associated with the first user based on the work unit records and/or the user records. By way of another example, unit of work component 114 may be configured to identify the one or more units of work that are associated with both the first user and the second user. A unit of work associated with both the first user and the second user may include a unit of work assigned to the first user by the second user, a unit of work the first user is responsible for completing and the second user is overseeing, a unit of work assigned to both the first user and the second user, a unit of work for a team both the first user and the second user are a part of, and/or other configurations. Work information corresponding to the units of work identified by unit of work component 114 may be included in the graphical user interfaces for individual ones of the users.

Graphical user interface component 116 may be configured to effectuate presentation of a graphical user interface corresponding to the user selected via the user input. The graphical user interfaces corresponding to the users may include stated information provided by the users, portions of one or more chat sessions the selected users and the selecting users (that selected to view the GUIs associated with the selected users) are participants in, and/or other information. In some implementations, graphical user interface component 116 may be configured to effectuate presentation of a first graphical user interface responsive to receiving user input indicating selection of the first user by the second user. The first graphical user interface corresponding to the first user may be presented via a client computing platform associated with the second user responsive to the second user selecting the first user. The first graphical user interface may represent chat sessions and/or units of work the first user and the second user have in common and/or share.

By way of non-limiting example, the first graphical user interface (provided in response to the second user selecting to view the GUI associated with the first user) may include first stated information provided by the first user, portions of one or more chat sessions the first user is a participant in with the second user, and/or other information. As such, the first graphical user interface may display the first stated information characterizing the first user, at least a portion of the first chat session, and at least a portion of the second chat session.

Stated information may include information inputted and/or selected by the users that characterizes the users and/or will be included in the graphical user interfaces associated with the users. The first stated information may include information selected and/or input by the first user that characterizes the first user. By way of non-limiting example, the first stated information may include username information, title information, department information, status information, personal information, and/or other information. A user may write, select, and/or determine what stated information is included in their graphical user interface regardless of the selecting user viewing their graphical user interface.

In some implementations, effectuating presentation of the graphical user interfaces corresponding to the users may include presenting work information for the one or more units of work identified by unit of work component 114 as being associated with the selected user and/or the selecting user. By way of non-limiting example, effectuating presentation of the first graphical user interface may include presenting work information for the one or more units of work identified as being associated with both the first user and the second user (that selected the first user), or presenting work information for the one or more units of work identified as being associated with only the first user.

Graphical user interface component 116 may be configured to effectuate presentation of a second graphical user interface corresponding to the second user. Presentation of the second graphical user interface may be effectuated responsive to receiving user input indicating selection of the second user by the first user. The second graphical user interface may be presented via a client computing platform associated with the first user. By way of non-limiting example, the second graphical user interface may include second stated information provided by the second user, portions of one or more chat sessions the second user is a participant in with the first user, and/or other information. As such, the second graphical user interface may display the second stated information, at least a portion of the first chat session, at least a portion of the second chat session, and/or other information. The graphical user interfaces may display portions of the chat sessions both the selected user and the selecting user are participants in. In some implementations, the graphical user interfaces may display portions of group chat sessions between other users in addition to the selected user and the selecting user.

Graphical user interface component 116 may be configured to effectuate presentation of a third graphical user interface corresponding to the third user responsive to receiving user input indicating a selection of the third user by the second user. The third graphical user interface corresponding to the third user may be presented via a client computing platform associated with the second user responsive to user selection component 112 receiving user input from the second user indicating a selection of the third user. The third graphical user interface may include third stated information provided by the third user, portions of one or more chat sessions the third user is a participant in with the second user, and/or other information. As such, the third graphical user interface may display the third stated information, at least a portion of the first chat session (between the first user, the second user, and the third user), and/or other information.

The portions of the one or more chat session displayed via one or more graphical user interfaces may include text information representing one or more of the communications input by an individual ones of the participants. For example, the portion of the first chat session displayed by the first graphical user interface may include one or more of the communications input by the first user, one or more communications input by the second user, and/or one or more communications input by the third user. Inputting communications may include The portion of the second chat session displayed by the first graphical user interface may include one or more of the communications input by the first user and/or one or more the communications input by the second user.

FIG. 2 illustrates a graphical user interface corresponding to user 1 and including portions of one or more chat sessions user 1 and user 2 are participants in, in accordance with one or more implementations. Graphical user interface 200 may correspond to User 1. User 2 may select User 1 to view graphical user interface 200. Graphical user interface 200 may include stated information 202. Stated information 202 may include a username (e.g., “User 1”), a department, a title (e.g., a job title), an about me section, and/or other information provided by and/or input by User 1. Graphical user interface 200 may include a portion of chat session 204, a portion of chat session 206, a portion of chat session 208, and/or other portions of other chat sessions User 1 and User 2 are participants in. User 1 and User 2 may be participants in chat session 204. User 1, User 2, and User 3 may be participants in chat session 206. User 1, User 2, and User 5 may participants in chat session 208. All of the chat sessions displayed via graphical user interface 200 may include at least User 1 and User 2 as participants responsive to User 2 selecting to view graphical user interface 200 corresponding to User 1.

FIG. 3 illustrates a graphical user interface corresponding to user 1 and including portions of one or more chat sessions user 1 and user 2 are participants in, in accordance with one or more implementations. Graphical user interface 300 may correspond to User 1. User 2 may select User 1 to view graphical user interface 300. Graphical user interface 300 may include stated information 302. Stated information 302 may include a username (e.g., “User 1”), a department, a title (e.g., a job title), an about me section, and/or other information provided by and/or input by User 1. Graphical user interface 300 may include a portion of chat session 304, a portion of chat session 306, a portion of chat session 308, and/or other portions of other chat sessions User 1 and User 2 are participants in. User 1 and User 2 may be participants in chat session 304. User 1, User 2, and User 3 may be participants in chat session 306. User 1, User 2, and User 5 may participants in chat session 308. All of the chat sessions displayed via graphical user interface 300 may include at least User 1 and User 2 as participants responsive to User 2 selecting to view graphical user interface 300 corresponding to User 1.

Graphical user interface 300 may include work information 310 for units of work 302. Work information 310 may comprise titles for units of work 302 both User 1 and User 2 are associated with. User 1 and User 2 may both be working on, assigned to, and/or associated with units of work 312. By way of example, User 2 may be the project manager for Project A and Project C (which User 1 is associated with). By way of another example, User 2 may have assigned one or more of Task 1, Task 2, Task 6, Task 9, and Task 10 to User 1.

Returning to FIG. 1, in some implementations, server(s) 102, client computing platform(s) 104, and/or external resources 118 may be operatively linked via one or more electronic communication links. For example, such electronic communication links may be established, at least in part, via a network such as the Internet and/or other networks. It will be appreciated that this is not intended to be limiting, and that the scope of this disclosure includes implementations in which server(s) 102, client computing platform(s) 104, and/or external resources 118 may be operatively linked via some other communication media.

A given client computing platform 104 may include one or more processors configured to execute computer program components. The computer program components may be configured to enable an expert or user associated with the given client computing platform 104 to interface with system 100 and/or external resources 118, and/or provide other functionality attributed herein to client computing platform(s) 104. By way of non-limiting example, the given client computing platform 104 may include one or more of a desktop computer, a laptop computer, a handheld computer, a tablet computing platform, a NetBook, a Smartphone, a gaming console, and/or other computing platforms.

External resources 118 may include sources of information outside of system 100, external entities participating with system 100, and/or other resources. In some implementations, some or all of the functionality attributed herein to external resources 118 may be provided by resources included in system 100.

Server(s) 102 may include electronic storage 120, one or more processors 122, and/or other components. Server(s) 102 may include communication lines, or ports to enable the exchange of information with a network and/or other computing platforms. Illustration of server(s) 102 in FIG. 1 is not intended to be limiting. Server(s) 102 may include a plurality of hardware, software, and/or firmware components operating together to provide the functionality attributed herein to server(s) 102. For example, server(s) 102 may be implemented by a cloud of computing platforms operating together as server(s) 102.

Electronic storage 120 may comprise non-transitory storage media that electronically stores information. The electronic storage media of electronic storage 120 may include one or both of system storage that is provided integrally (i.e., substantially non-removable) with server(s) 102 and/or removable storage that is removably connectable to server(s) 102 via, for example, a port (e.g., a USB port, a firewire port, etc.) or a drive (e.g., a disk drive, etc.). Electronic storage 120 may include one or more of optically readable storage media (e.g., optical disks, etc.), magnetically readable storage media (e.g., magnetic tape, magnetic hard drive, floppy drive, etc.), electrical charge-based storage media (e.g., EEPROM, RAM, etc.), solid-state storage media (e.g., flash drive, etc.), and/or other electronically readable storage media. Electronic storage 120 may include one or more virtual storage resources (e.g., cloud storage, a virtual private network, and/or other virtual storage resources). Electronic storage 120 may store software algorithms, information determined by processor(s) 122, information received from server(s) 102, information received from client computing platform(s) 104, and/or other information that enables server(s) 102 to function as described herein.

Processor(s) 122 may be configured to provide information processing capabilities in server(s) 102. As such, processor(s) 122 may include one or more of a digital processor, an analog processor, a digital circuit designed to process information, an analog circuit designed to process information, a state machine, and/or other mechanisms for electronically processing information. Although processor(s) 122 is shown in FIG. 1 as a single entity, this is for illustrative purposes only. In some implementations, processor(s) 122 may include a plurality of processing units. These processing units may be physically located within the same device, or processor(s) 122 may represent processing functionality of a plurality of devices operating in coordination. Processor(s) 122 may be configured to execute components 108, 110, 112, 114, and/or 116, and/or other components. Processor(s) 122 may be configured to execute components 108, 110, 112, 114, and/or 116, and/or other components by software; hardware; firmware; some combination of software, hardware, and/or firmware; and/or other mechanisms for configuring processing capabilities on processor(s) 122. As used herein, the term “component” may refer to any component or set of components that perform the functionality attributed to the component. This may include one or more physical processors during execution of processor readable instructions, the processor readable instructions, circuitry, hardware, storage media, or any other components.

It should be appreciated that although components 108, 110, 112, 114, and/or 116 are illustrated in FIG. 1 as being implemented within a single processing unit, in implementations in which processor(s) 122 includes multiple processing units, one or more of components 108, 110, 112, 114, and/or 116 may be implemented remotely from the other components. The description of the functionality provided by the different components 108, 110, 112, 114, and/or 116 described below is for illustrative purposes, and is not intended to be limiting, as any of components 108, 110, 112, 114, and/or 116 may provide more or less functionality than is described. For example, one or more of components 108, 110, 112, 114, and/or 116 may be eliminated, and some or all of its functionality may be provided by other ones of components 108, 110, 112, 114, and/or 116. As another example, processor(s) 122 may be configured to execute one or more additional components that may perform some or all of the functionality attributed below to one of components 108, 110, 112, 114, and/or 116.

FIG. 4 illustrates a method 400 for presenting graphical user interfaces corresponding to users and including portions of one or more chat sessions the users are participants in, the chat sessions facilitating synchronous textual communication between the users that takes place through a chat system, in accordance with one or more implementations. The operations of method 400 presented below are intended to be illustrative. In some implementations, method 400 may be accomplished with one or more additional operations not described, and/or without one or more of the operations discussed. Additionally, the order in which the operations of method 400 are illustrated in FIG. 4 and described below is not intended to be limiting.

In some implementations, method 400 may be implemented in one or more processing devices (e.g., a digital processor, an analog processor, a digital circuit designed to process information, an analog circuit designed to process information, a state machine, and/or other mechanisms for electronically processing information). The one or more processing devices may include one or more devices executing some or all of the operations of method 400 in response to instructions stored electronically on an electronic storage medium. The one or more processing devices may include one or more devices configured through hardware, firmware, and/or software to be specifically designed for execution of one or more of the operations of method 400.

An operation 402 may include obtaining chat information characterizing participants in the chat sessions. The chat sessions may include a first chat session and a second chat session. The first chat session may facilitate synchronous textual communication between a first user, a second user, and a third user, such that first chat information characterizing the first user, the second user, and the third user as participants in the first chat session is obtained. The second chat session may facilitate synchronous textual communication between the first user and the second user such that second chat information characterizing the first user and the second user as participants in the second chat session is obtained. Operation 402 may be performed by one or more hardware processors configured by machine-readable instructions including a component that is the same as or similar to chat component 110, in accordance with one or more implementations.

An operation 404 may include effectuating presentation, responsive to receiving user input indicating a selection of the first user by the second user, of a first graphical user interface corresponding to the first user via a client computing platform associated with the second user. The first graphical user interface may include first stated information provided by the first user and portions of one or more chat sessions the first user is a participant in with the second user. As such, the first graphical user interface may display the first stated information characterizing the first user, at least a portion of the first chat session, and at least a portion of the second chat session. Operation 404 may be performed by one or more hardware processors configured by machine-readable instructions including a component that is the same as or similar to graphical user interface component 116, in accordance with one or more implementations.

FIG. 5 illustrates a method 500 for presenting graphical user interfaces corresponding to users and including portions of one or more chat sessions the users are participants in, the chat sessions facilitating synchronous textual communication between the users that takes place through a chat system, in accordance with one or more implementations. The operations of method 500 presented below are intended to be illustrative. In some implementations, method 500 may be accomplished with one or more additional operations not described, and/or without one or more of the operations discussed. Additionally, the order in which the operations of method 500 are illustrated in FIG. 5 and described below is not intended to be limiting.

In some implementations, method 500 may be implemented in one or more processing devices (e.g., a digital processor, an analog processor, a digital circuit designed to process information, an analog circuit designed to process information, a state machine, and/or other mechanisms for electronically processing information). The one or more processing devices may include one or more devices executing some or all of the operations of method 500 in response to instructions stored electronically on an electronic storage medium. The one or more processing devices may include one or more devices configured through hardware, firmware, and/or software to be specifically designed for execution of one or more of the operations of method 500.

An operation 502 may include managing environment state information for maintaining a collaboration environment. The environment state information may include user records, work unit records, and/or other records. The environment state information may define a state of the collaboration environment including user states, a work unit state, and/or other states. The user states may be defined by the user records that define values of user parameters associated with users interacting with and/or viewing the collaboration environment. The work unit states may be defined by the work unit records that define values of work unit parameters for units of work managed, created, and/or assigned within the collaboration environment. Operation 502 may be performed by one or more hardware processors configured by machine-readable instructions including a component that is the same as or similar to environment state component 108, in accordance with one or more implementations.

Operation 504 may include obtaining chat information characterizing participants in the chat sessions. The chat sessions may include a first chat session and a second chat session. The first chat session may facilitate synchronous textual communication between a first user, a second user, and a third user, such that first chat information characterizing the first user, the second user, and the third user as participants in the first chat session is obtained. The second chat session may facilitate synchronous textual communication between the first user and the second user such that second chat information characterizing the first user and the second user as participants in the second chat session is obtained. Operation 504 may be performed by one or more hardware processors configured by machine-readable instructions including a component that is the same as or similar to chat component 110, in accordance with one or more implementations.

Operation 506 may include receiving user input indicating selection of a first user by the second user. Operation 506 may be performed by one or more hardware processors configured by machine-readable instructions including a component that is the same as or similar to user selection component 112, in accordance with one or more implementations.

Operation 508 may include identifying one or more units of work associated with the first user. The one or more units of work associated with the first user may be identified based on the work unit records and/or the user records. Operation 508 may be performed by one or more hardware processors configured by machine-readable instructions including a component that is the same as or similar to unit of work component 114, in accordance with one or more implementations.

An operation 510 may include effectuating presentation, responsive to receiving user input indicating a selection of the first user by the second user, of a first graphical user interface corresponding to the first user via a client computing platform associated with the second user. The first graphical user interface may include first stated information provided by the first user, portions of one or more chat sessions the first user is a participant in with the second user, and work information for the one or more units of work identified as being associated with the first user. As such, the first graphical user interface may display the first stated information characterizing the first user, at least a portion of the first chat session, at least a portion of the second chat session, and work information for the one or more units of work identified as being associated with the first user. Operation 510 may be performed by one or more hardware processors configured by machine-readable instructions including a component that is the same as or similar to graphical user interface component 116, in accordance with one or more implementations.

Although the present technology has been described in detail for the purpose of illustration based on what is currently considered to be the most practical and preferred implementations, it is to be understood that such detail is solely for that purpose and that the technology is not limited to the disclosed implementations, but, on the contrary, is intended to cover modifications and equivalent arrangements that are within the spirit and scope of the appended claims. For example, it is to be understood that the present technology contemplates that, to the extent possible, one or more features of any implementation can be combined with one or more features of any other implementation. 

What is claimed is:
 1. A system configured to present a graphical user interface displaying information from multiple different chat session that share common participants, the system comprising: one or more hardware processors configured by machine-readable instructions to: effectuate presentation of a graphical user interface via a client computing platform, the graphical user interface corresponding to multiple users who were participants in multiple different chat sessions, the graphical user interface displaying information stated by at least one of the multiple users in the multiple different chat sessions, such that the graphical user interface displays a portion of one of the multiple different chat sessions, and an other portion of an other one of the multiple different chat sessions.
 2. The system of claim 1, wherein the one or more hardware processors are further configured by the machine-readable instructions to: manage environment state information for maintaining a collaboration environment, the environment state information including work unit records, the work unit records including work information for units of work managed, created, and/or assigned within the collaboration environment; identify one or more of the units of work associated with the at least one of the multiple users; and wherein effectuating presentation of the graphical user interface includes presenting the work information for the one or more of the units of work.
 3. The system of claim 2, wherein the one or more of the units of work are identified as being associated with all of the multiple users.
 4. The system of claim 1, wherein the portion of the one of the multiple different chat sessions includes communications input by the at least one of the multiple users, and/or the other portion of the other one of the multiple different chat sessions includes other communications input by the at least one of the multiple users.
 5. The system of claim 1, wherein the portion of the one of the multiple different chat sessions includes communications input by an other one of the multiple users, and/or the other portion of the other one of the multiple different chat sessions includes other communications input by the other one of the multiple users.
 6. The system of claim 2, wherein the one or more hardware processors are further configured by the machine-readable instructions to: implement an instance of a chat session to facilitate synchronous textual communications between the multiple users within the collaboration environment, and transmit the textual communications that make up the chat session to client computing platforms for presentation through graphical chat interfaces.
 7. The system of claim 1, wherein the graphical user interface is presented responsive to a user associated with the client computing platform providing user input indication a selection of the at least one of the multiple users.
 8. The system of claim 7, wherein the user is one of the multiple users.
 9. The system of claim 1, wherein the portion of the one of the multiple different chat sessions and the other portion of the other one of the multiple different chat sessions includes information inputted or selected by the at least one of the multiple users.
 10. The system of claim 1, wherein the information stated by the at least one of the multiple users includes one or more of username information, title information, department information, status information, or work information.
 11. A method to present a graphical user interface displaying information from multiple different chat session that share common participants, the method being implementation in a computer system comprising one or more physical processors configured by machine-readable instructions, such that execution of the machine-readable instructions by the one or more physical processors causes the one or more physical processor to perform the method comprising: effectuating presentation of a graphical user interface via a client computing platform, the graphical user interface corresponding to multiple users who were participants in multiple different chat sessions, the graphical user interface displaying information stated by at least one of the multiple users in the multiple different chat sessions, such that the graphical user interface displays a portion of one of the multiple different chat sessions, and an other portion of an other one of the multiple different chat sessions.
 12. The method of claim 11, further comprising: managing environment state information for maintaining a collaboration environment, the environment state information including work unit records, the work unit records including work information for units of work managed, created, and/or assigned within the collaboration environment; identifying one or more of the units of work associated with the at least one of the multiple users; and wherein the effectuating presentation of the graphical user interface includes presenting the work information for the one or more of the units of work.
 13. The method of claim 12, wherein the one or more of the units of work are identified as being associated with all of the multiple users.
 14. The method of claim 11, wherein the portion of the one of the multiple different chat sessions includes communications input by the at least one of the multiple users, and/or the other portion of the other one of the multiple different chat sessions includes other communications input by the at least one of the multiple users.
 15. The method of claim 11, wherein the portion of the one of the multiple different chat sessions includes communications input by an other one of the multiple users, and/or the other portion of the other one of the multiple different chat sessions includes other communications input by the other one of the multiple users.
 16. The method of claim 12, further comprising: implementing an instance of a chat session to facilitate synchronous textual communications between the multiple users within the collaboration environment, and transmit the textual communications that make up the chat session to client computing platforms for presentation through graphical chat interfaces.
 17. The method of claim 11, wherein the graphical user interface is presented responsive to a user associated with the client computing platform providing user input indication a selection of the at least one of the multiple users.
 18. The method of claim 17, wherein the user is one of the multiple users.
 19. The system of claim 11, wherein the portion of the one of the multiple different chat sessions and the other portion of the other one of the multiple different chat sessions includes information inputted or selected by the at least one of the multiple users.
 20. The system of claim 11, wherein the information stated by the at least one of the multiple users includes one or more of username information, title information, department information, status information, or work information. 